Battery monitoring network

ABSTRACT

A battery monitoring network including a battery node ( 6 ); one or more distributed nodes of a first class ( 4 ) each including means for acquiring first battery variable information, processing means adapted to manipulate the first battery variable information, and a communication means for communicating with a battery node; and one or more distributed nodes of a second class ( 5 ) each including means for acquiring second battery variable information, processing means adapted to manipulate the second battery variable information, and a communication means for communicating with the battery node.

FIELD OF THE INVENTION

[0001] The invention relates to a battery monitoring network.

BACKGROUND TO THE INVENTION

[0002] Battery management objectives may be summarised as a) providing accurate and timely information on the battery reserve time, b) providing accurate and timely information on remaining battery life, c) providing recommendations to the optimal charging process that will allow for efficient charge recovery without sacrificing battery health, and d) informing the user on any possible maintenance action that supports system integrity. To meet these objectives continuous monitoring of real-time battery variables and trend data should take place. However, some battery monitors are still based on simple data logging that is supported by limit sensing. Centralised approaches in cell, or bloc, signal sensing is still dominant in the existing systems. Furthermore, a good part of the information extraction scenarios are far from being automated with most of the analysis being operator driven and tests conducted on a periodic basis.

[0003] Efficient management of a battery network requires the smooth flow of timely and consistent information/data from the battery units (blocs, groups, strings and banks) to the various monitoring, management and control sites. The main issue related to implementing of real-time battery monitoring is voltage, temperature and current measurement. In particular, the ability to acquire accurate and timely voltage measurements is critical. The accuracy and resolution of the voltage measurement directly impacts on the accuracy and resolution of the derived information. This is especially important for capacity estimation utilising the Coup De Fouet region. For thorough implementation (down to bloc level), the system is required to monitor the voltage of each bloc at the start of discharge at a frequency of up to 1 Hz.

[0004] However, battery networks vary in size. Systems could be as small as two strings of 24V mono-blocs. On the other hand, large systems could have tens of strings containing 24 blocs each. Normal practice is to partition the battery into a number of four string banks. Each string may contain blocs that are 2, 4, 6, or 12 volts. The 12-volt may be used as the common grouping factor that promotes relating the adjacent cells, whether they are six cells within a 12-volt mono-bloc or six individual adjacent blocs. The result is the need for substantial amounts of information to be acquired and processed in real-time. This causes considerable traffic overflow within the monitoring network in the case of centralising the data processing.

[0005] Recently, the Internet connectivity to the site has also been encouraged. The approach presented is based on site-central connectivity. One approach is presented by O. Ludin in “An Operation and Maintenance Process Model for Energy Management” [Proceedings of the 21th International Telecommunication Energy Conference; Jun. 6-9, 1999, Copenhagen, 28-1 (7 pages)] which is based on the site as a Simple Network Management Protocol (SNMP) agent that interacts with the remote station using what is called energy management application software. Another approach is described in “Controlling and Alarming DC Power Plants via the Internet” [Proceedings of the 20th International Telecommunication Energy Conference; Oct. 4-8, 1998, San Francisco, PP 617-22, A. Cosentino & M. Sullivan] which implements the connectivity using a gateway that is based on an embedded PC operated by QNX real time operating system. However, both solutions are cost sensitive and limit the site to a central connection point.

[0006] A battery monitoring network is described in U.S. Pat. No. 6,104,967. A number of modules communicate with a central battery computer. The modules each include module computers which monitor various operations and status conditions within the module, including potential, current, and temperature conditions.

[0007] It is an object of the present invention to provide a generic network architecture for a battery monitoring system which can be implemented on existing open standard network protocols, is cost effective and efficient, and is inherently suited to internet connectivity; or to provide a system which at least overcomes or ameliorates some of the disadvantages with the prior art, or provides industry with a useful alternative.

[0008] Further aspects of the invention will become apparent from the following description.

SUMMARY OF THE INVENTION

[0009] In a first aspect the invention provides a battery monitoring network including a battery node; one or more distributed nodes of a first class each including means for acquiring first battery variable information, processing means adapted to manipulate the first battery variable information, and a communication means for communicating with the battery node; and one or more distributed nodes of a second class each including means for acquiring second battery variable information, processing means adapted to manipulate the second battery variable information, and a communication means for communicating with the battery node.

[0010] By using two different classes of distributed node (in contrast to U.S. Pat. No. 6,104,967 which has only a single class of distributed node), the present invention provides a more flexible network configuration. Each different class of node can also be optimised to deal with the particular type of information (for instance, voltage, temperature or current) that it is acquiring and manipulating.

[0011] Intelligence is distributed to a number of separate nodes, which may perform a variety of data manipulation algorithms to calculate various parameters such as reserve charge, coup de fouet parameters, reserve time etc. The distributed nodes may also compare the acquired battery variable information with one or more predetermined thresholds. The distributed nodes may also store historical information.

[0012] The distributed nodes may communicate with the battery node via a star-network configuration, or via a common bus. The use of a common bus is preferable since this also allows the distributed nodes to communicate with each other independently of the battery node.

[0013] Preferably the distributed nodes are arranged in two or more sub-networks, each sub-network communicating with the battery node via a respective sub-network junction

[0014] Preferably, but not exclusively, each sub-network is interconnected by a router or other network interconnection means. Alternatively, each sub-network may be interconnected at the battery node.

[0015] Preferably the first class of distributed nodes are bloc nodes which each acquire information (typically voltage and/or temperature information) from a bloc of one or more serially connected cells, more preferably six cells. Typically a separate voltage reading is acquired from each cell. The temperature information may be bloc and/or ambient temperature.

[0016] Preferably the second class of distributed nodes are bank nodes which acquire information (typically current information) from of one or more serially connected blocs, conventionally known as a string, the strings being connected in parallel with each other. Preferably the bank nodes also store and manipulate trend and/or analysis information relating to the strings.

[0017] Preferably although not exclusively each sub-network has up to sixty-four nodes accommodating up to three banks (or strings) that comprises forty-eight bloc nodes.

[0018] Preferably the battery node is adapted to store and manipulate trend and/or analysis information. The battery node may store and manipulate trend and/or analysis information relating to one or more sub-networks which are interconnected by a router or other network interconnection means. Alternatively, there may be a battery node associated with each sub-network, the sub-networks being interconnected by the battery nodes.

[0019] Preferably the battery node includes a user interface and more preferably a graphical user interface. The battery node may also be coupled to an internet interface for remote access of battery information. A local user may also interface with the monitoring network via the battery node.

[0020] Preferably the operation and function of each node is configurable at the battery node.

[0021] In a second aspect the invention provides for a distributed knowledge based battery monitoring architecture for organising information in a battery monitoring system including, separating the information into a hierarchy having at least two levels wherein a first, or bloc, level comprises information relating to the real-time bloc temperatures and voltages and a second, or bank, level comprises information relating to string current and inter-bloc voltages and temperatures. Preferably the hierarchy has three levels, a third, or battery, level comprising information relating to inter-string current analysis, data and information buffering and user interface screens.

[0022] The invention also provides for a battery monitoring system organised according to the above architecture.

[0023] Further aspects of the invention will become apparent from the following description which is given by way of example only and with reference to the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The invention will now be described with reference to the accompanying drawings in which:

[0025]FIG. 1: illustrates a Battery Management System Architecture according to the invention,

[0026]FIG. 2: illustrates Voltage vs. State-of-Charge at the Bloc level of the Battery Management System Architecture,

[0027]FIG. 3: illustrates node links and responsibilities at the Bloc level of the Battery Management System Architecture,

[0028]FIG. 4: illustrates the accuracy and sampling rate needed at the Coup de Fouet region,

[0029]FIG. 5: illustrates node responsibilities and interconnections at the Bank level of the Battery Management System Architecture,

[0030]FIG. 6: illustrates infranet interface responsibility and interconnection at the Battery level of the Battery Management System Architecture,

[0031]FIG. 7: illustrates internet interface responsibilities and interconnection at the Battery level of the Battery Management System Architecture,

[0032]FIG. 8: illustrates a sectioned voltage curve for a single cell at a Bloc Node,

[0033]FIG. 9: illustrates a user interface view showing real-time status of variables at various nodes of the Battery Management System Architecture,

[0034]FIG. 10: illustrates a user interface view showing history trend,

[0035]FIG. 11: illustrates a user interface view showing battery configuration,

[0036]FIG. 12: illustrates a user interface alarm page, and

[0037]FIG. 13: illustrates an alternative network architecture.

DESCRIPTION OF THE PREFERRED EXAMPLE

[0038] The invention will now be described with reference to the architecture for a VRLA battery management environment that allows for integration with the rest of a telecommunication power system. While the invention is described with reference to a telecommunication battery system the invention provides a generic battery monitoring and management architecture which may be applied to any battery installation. The generic battery monitoring and management architecture of the invention allows for a) a generic platform for knowledge distribution and information/data structures, b) a local communication organisation which allows the architecture to be implemented on a proprietary control network, c) internet connectivity and remote communication organisation, and d) remote management, technical support and site collaboration.

[0039] In the following example of the invention there is a network architecture that monitors battery condition based on a number of generic monitoring nodes. Monitoring responsibilities are shared among these nodes. The solution is modular and allows for covering a wide range of battery networks using the same architecture and generic nodes.

[0040] In the example described the local network is based on LonWorks™ which provides the necessary environment for open system interconnection. However, it will be apparent to the skilled addressee that the architecture could be applied to other network platforms. The LonWorks™ Neuron chips allow for knowledge elements to be embedded within the local node. The network is organised so as to provide access to the battery bloc(s), string(s), and system. Each node is made responsible for a number of activities related to the associated bloc(s). Both real time and trend analyses are made locally.

[0041] The Internet interface is based on an embedded Java environment. Internet access could be made available to any device within the network either through a common or specific gateway. Connectivity could be organised on a battery level or even a battery sub-net level, allowing each sub-net to be connected or isolated individually. The organisation facilitates an environment for structuring the battery knowledge that allows a consistent and effective user interface for battery management. Integration with the rest of the power system could be made through the Internet, allowing for full implementation of system management actions such as smart charge control.

[0042] Network Architecture

[0043] Batteries are categorised as being loosely coupled to the system within the telecommunication power system. They contribute to the support of the load when the rectifiers are down. They are living at float voltage most of the time. When charging, or when a discharge test is conducted, the process will be pre-programmed. They could therefore be considered as being loosely coupled to the system. Parts of the battery could be isolated or integrated without affecting the integrity of the system. This allows the battery management to be a class of its own. A network organisation to this class may have its own natural structure. It may also be considered as a sub-net within the rest of the power system network.

[0044] A first example of a management system architecture is illustrated by FIG. 1. The network is partitioned into a group of sub-nets, each of which contains a number of bank nodes and bloc nodes. Each bank node acquires current from four battery strings (not shown). Each string is partitioned into groups of cells, each group of cells being a bloc. The bloc nodes each acquire real time data from a respective battery bloc. In the system of FIG. 1, each battery sub-network accommodates up to three bank nodes, each bank node monitoring four strings with each string being made up of four blocs of six two-volt cells. In this case the sub-network will monitor twelve 48V strings. In an alternative configuration (not shown) the sub-network may be configured to monitor twenty-four 24V strings. When the network required is larger than the sub-network capacity, routers are used to connect more than one LonWorks™ sub-network to the network. An alternative to the use of routers is the use of the Internet gateway for each sub-net. Using the Internet would however introduce some latency in real-time interaction as related to the battery information integrity.

[0045] A battery node acts as the network gateway to the Internet. Two processing units are implemented here. The first is the Infranet interface and the second is the Internet interface. Communication between these two units is done through an RS232 serial bus. The Internet interface acts as a gateway to the Internet supporting the flow of battery data and information. This allows one or more remote mangers to communicate with the battery network by interrogating the various nodes. It also allows for a local manager to communicate with the network.

[0046] A repository of medium-term battery information and historical data is facilitated at the battery node. Here the battery node provides a central data point to the local and various remote management stations, maintaining consistency in handling battery monitoring and management actions. The Internet interface also has a provision for facilitating routing to a CAN network.

[0047] This organisation allows for accessing the individual blocs. The various nodes related to blocs, strings and battery, exercise data processing as well as communication. Basic knowledge elements are distributed among the nodes, allowing each of these nodes to play a role in inferring short-term battery conditions. Involved knowledge elements related to long-term analysis are located at the service centre. Both remote and local managers utilise such analysis.

[0048] Local Network

[0049] The local network is referred to as the network that links the computation facilities at the battery site. This covers the bloc nodes, the bank nodes, the battery node and the local manager station. These are considered as the core elements that co-operate in performing the data acquisition, data processing, short-term data and information logging and configuration of the battery monitoring system. The local user interaction is also considered as part of this network. The local manager provides a local access to the battery information.

[0050] A LonWorks™ peer-to-peer network based on ISO/OSI seven-layer model of open system interconnection has been used as a typical example for a commercially available technology. LON nodes are capable of being application specific intelligent devices. Knowledge could be embedded into each of these nodes to make them perform dedicated activities related to battery data acquisition and processing. The addressing supports large networks with multiple channels and allows the implementation of low cost routers.

[0051] Bloc Node

[0052] The bloc node is designed to cater for monitoring a group of six two-volt cells. This provides a trade-off between the processing requirements of the bloc node and the size of the sub-network. It also promotes the design of internal cell monitoring of a twelve-volt mono-bloc as an embedded solution. The channel electrical characteristics of 78 kbps twisted pair media limits the number of subnetwork nodes to 64, allowing for up to 12 strings of 48V. The bloc node provides pilot temperature sensing for the group of six cells as well as close-by-ambient temperature sensing.

[0053] The bloc node acquires voltage samples at a rate of one per second, representative readings being sent over the network at a rate of up to once every 10 seconds. The bloc node also samples the temperature once every 30 seconds and evaluates the state of charge once every minute. This is based on the voltage vs. state-of-charge relationship which is described in the Applicant's earlier patent application published as WO 00/13288. It does perform other functions. The responsibilities of the bloc node are summarised by the following:

[0054] Acquire the group data related to voltages and temperatures.

[0055] Establish a short-term data and information history related to the group.

[0056] Work out lowest and average reserve charge on discharge.

[0057] Detect the coup de fouet parameters just after the start of the discharge (see FIG. 4).

[0058] Detect end voltage.

[0059] Detect inter-bloc maximum & minimum.

[0060] Communicate with the network.

[0061] Retain identification of the group.

[0062] Retain short term history on group data and status conditions

[0063] Calculate temperature or voltage limit violations—for example calculate voltage difference between cells in each bloc and determine whether this has exceeded a predetermined maximum, or calculate difference between bloc temperature and ambient temperature and determine whether this has exceeded a predetermined maximum

[0064] Each of the bloc nodes samples the associated bloc voltages, pilot bloc temperature and close-by ambient temperature at a rate appropriate to battery needs. Measurement accuracy and sampling rate should be sufficient to cater for capturing meaningful events. The most critical information that requires high accuracy and sampling rate is the start of discharge parameters (see FIG. 4). Investigation related to this region has reflected its significance in providing information on the battery capacity. This is described in Applicant's earlier patent application Number PCT/NZ00/00089. The samples are checked against previous samples and considered for logging and processing when they present a predefined incremental change, a maximum or a minimum. A limited memory is allocated for the short term logging of the data and events related to each bloc.

[0065] Processing at the bloc node provides information related to bloc reserve charge and bloc limit violations. It also discovers essential information related to the start of the discharge. The bank node communicates with the bloc node for deriving the string-related information, as described in more detail below. Messages related to bloc data and events are sent to the battery node, which acts as a gateway to the external world. Configuration messages related to this node will also be received from the battery node. These are mainly related to alarm limits, state of charge characterisation as well as initial battery identification.

[0066] The bloc node could be physically attached to or embedded in the battery bloc/cell.

[0067] Bank Node

[0068] The bank node fulfils the job of string management and inter-string monitoring. This handles up to four strings. It acquires the string currents at a rate of one sample per second. The current value is used in detecting the switching in string operational status (i.e. charge to discharge and vice versa). It is also used to calculate and hence report on the remaining time of the lowest and average bloc for each string during discharge. The node also determines the voltage and temperature spread for each string (based on data received from the bank nodes associated with each string) and reports on any conditions that exceed the set limits. This will allow the upper level computational units where the database resides, to work out the persistence in each of these elements and to issue relevant alarms. The following are a summary of the bank node responsibilities:

[0069] Work out the string spreads for inter-bloc voltages, inter-group temperature and identify any violations of the set limits of these spreads.

[0070] Acquire string currents.

[0071] Establish short-term string level history.

[0072] Identify string status (charging or discharging), and inform bloc nodes of status change events.

[0073] Communication with the network.

[0074] Determining string minimum and average reserve time.

[0075] Battery Node

[0076] The battery node is responsible for interfacing the LON battery Infranet to the external world. Here bidirectional message flow is facilitated. This will allow information related to battery data and events to flow upward to the battery database. It will also allow commands for network configuration or information queries to flow downward to the various nodes.

[0077] Two main units are co-operating at this node. These are a) Infranet (LON) Interface and b) Internet Interface. The Infranet interface provides the LonWorks™ gateway to the Internet interface. The Internet interface connects the battery Infranet to the local and remote management stations. The roles of each of these units are given in the following sections.

[0078] Infranet Interface

[0079] This unit facilitates the interface between the Infranet and the Internet interface unit. Data on each string is updated as it is received through the network. It will then be forwarded to the Internet interface unit once every 10 seconds. The current spread of all strings is analysed. When this spread exceeds the limit a message will be sent to the Internet interface at a pre-specified interval. The following responsibilities are allocated to the Battery Node:

[0080] Analyse string current spread.

[0081] Work out the battery wide average and worst case reserve time.

[0082] Communicate with bloc and string nodes.

[0083] Communicate with Internet interface.

[0084] Establish medium term history on battery data and status

[0085] Real time battery data and events are received by this node and passed to the Internet interface unit. The data is clustered in a string-by-string basis. This allows room for some significant data compression. Commands are received from the Internet interface unit related to node configuration or request for information from any of the working nodes. These are translated into LON messages and forwarded to the associated node. This node is also responsible for catering with battery-wide inter-string comparison and battery reserve time.

[0086] The mechanism for communication between the Infranet interface and Internet interface will play a major role in determining the information flow capacity. A good percentage of telecommunication sites have less than 12 strings (one sub-network). Here, a software solution would be sufficient to absorb the network requirement. Further expansion to increase the communication speed is also possible through a hardware solution. One option is to have one Internet interface per sub-net. The size of the associated battery system would justify the cost. This will also provide redundancy that will ensure system security as well as design simplicity and cost optimisation.

[0087] Internet Interface

[0088] Battery information could be utilised by a number of clients. A site technician might view it locally. A remote service centre or one or more remote managers may also be associated with the system. The Internet is now receiving much greater acceptance within the telecommunication community. Integration of voice and data networks is good evidence to that. The network interface maintains the following requirements:

[0089] Information integrity and consistency.

[0090] Information security and access control.

[0091] Compatible network performance.

[0092] The use of an Internet gateway to interconnect the LonWorks™ network to the various remote sites would provide the infrastructure for the interface requirement. This has to be associated with other functionality that allow for the required consistence and access control.

[0093] The system interface is the gateway for interconnecting the LonWorks™ battery network to the Internet. This has been implemented using the Dallas TINI™ Internet interface product. The TINI™ is based on an embedded Java Virtual Machine (JVM). In addition the platform has a multitasking real time scheduler that allows for up to sixteen concurrent tasks. The Internet protocol is supported by the necessary TCP/IP network stack. These resources provide reasonable backup for the interfacing requirement. The unit supports a substantial storage backup that could be utilised for medium-term battery history. This provides a central point for accessing the battery real time and trend data.

[0094] The roles allocated to the Internet interface are summarised below:

[0095] Establish medium term battery database.

[0096] Compress battery data.

[0097] Generate information summary.

[0098] Provides/Updates the user interaction Applets to the remote users through the Internet.

[0099] Communicate with remote user via the Internet (TCP/IP Protocol).

[0100] Communicate with local user via the Intranet or the RS232 serial bus.

[0101] Communicate with battery network via the RS232 serial bus.

[0102] The Internet interface may also be used to perform battery management activities like battery capacity tests or battery charging.

[0103] Data Compression

[0104] Data compression is an important aspect of the battery central interaction point. Due to the limited size of the available backup storage, effective compression is needed to cover a good part of present (real-time) and nearby history of the battery behaviour. This helps in improving performance in terms of network traffic and speed of retrieval.

[0105] The compression strategy is based on both logical and signal analysis of the battery system. The following aspects are taken into consideration in system logical partitioning:

[0106] Group the data on a string-by-string basis.

[0107] Partition the trend into the main regions of charge, float and discharge (see FIG. 8).

[0108] Partition each of the these regions into fast and slow varying regions (see FIG. 8)

[0109] Apply an appropriate compression method for each of these parts. The method should be able to retain the key information/data that is relevant to that region.

[0110] The data to be stored is made up of two main aspects, system messages/alarms, and historical data. The majority of relevant information is in the form of historical data. This needs to be the focus of compression.

[0111] Most of the analysis is based on the voltage curves of the battery. To effectively compress and store these curves the curve is split into different sections according to string status and signal rate of variations. For example, to reconstruct the coup de fouet region effectively, a much larger number of samples per unit time would be needed than other parts of the discharge curve. A possible method of sectioning a common charge and discharge curve is shown below in FIG. 8.

[0112] Before the compression takes place, the Internet interface must decide on the status of the string. This is done either by notification from the bank node as the change of status takes place, or by the Internet interface interpreting change in status.

[0113] In a slowly varying region, a reading is stored when the voltage of the fastest varying bloc is exceeding a predefined increment.

[0114] For the fast varying sections of the voltage curve, there are many possible techniques that could be used for data compression. A similar technique to that used for the slowly varying signals may be used. This threshold value can be set according to how accurately the curve is to be reconstructed. An alternative method that has the potential to store the data more effectively is to use polynomial fitting to the different parts of the curve. This however, introduces processing overhead on the TINI™ during the time of compression or reconstruction.

[0115] To minimise the actual space that the data uses on the Internet interface's battery-backed RAM file system, the data is stored in a custom database with the data types being appropriate to the range and accuracy of the readings. The data is stored in a compact binary format to fully utilise the available memory. The timestamp is converted to Julian time before storing in the database.

[0116] Further minimisation could be made by monitoring the behaviour of the majority of blocs and accordingly deal with the bloc in isolation or as part of the string. Here, if more than half of the cells in the string are at a higher rate than the rest, all the string voltages will be recorded with one timestamp at that higher rate. If less than half the cells are recording at a higher rate, then these cells will be saved to the database individually. This is because the timestamp takes the same space as a single reading for a single cell of the string (two bytes), so this configuration will minimise the space used of the database.

[0117] Local Manager

[0118] A local manager may access the network for regular routine checks or for performing system installation or maintenance. The access to the network is made through the system interface. The user may be able to view real time battery data and messages or historical information from the battery database within the TINI™. The user may also perform system configuration or battery tests as authorised by the service centre. The local manager may also be authorised by the service centre in conducting required tests. The responsibilities of the local manager are summarised as follows:

[0119] Physical node structure configuration

[0120] Real-time data display

[0121] Messages and alarms

[0122] Historical information (trends and events)

[0123] Test schedule

[0124] Remote Manager

[0125] The site associated remote manager assumes authority over any critical maintenance action related to the site. This includes nodes configuration, battery testing, bloc replacement etc. The remote manager can also view the battery real time and trend data and messages. Both medium and long-term history could be used. A remote manager can be located anywhere on the global Internet. Collaborative elements within the monitoring views would allow the remote manager to authorise the service centre in conducting a test.

[0126] Service Centre

[0127] The service centre acts as the maintenance consultation centre. It stores the long-term historical data and alarm messages related to the battery. It also co-ordinates with both remote managers and the site manger in conducting a battery test. The service centre will also handle any requests for trend information that have expired from the Internet interface's medium-term database. The site manager may assume the role of this centre.

[0128] User Interface Views

[0129] Remote interaction with the battery system is done through Java applets. They are hosted at the TINI™ to support the user interaction at each of the remote sites. These Applets will facilitate the various interactive views. These views should address the various forms of access each remote or local station may have and relate to their responsibilities.

[0130]FIGS. 9, 1011 and 12 show sample views of a possible user interface applet. A tree-view on the left-hand side of each screen is used for navigation of all the nodes in the system. The user is able to change between all the different available views for any node in the system, while still using the same screen method for navigating these views. This provides a familiar and consistent feel. All the details of the system data, trends, alarms, events, configuration details and the test management schedule are shown in the right-hand section of the window as they are selected. The multiple dimensional browsing provides effective and fast interaction with the data and information delivered by the system.

[0131] The alarm and events screens allow the user to browse through the alarms and events chronologically. The tree provides a filter to the information you want to display. The numbers at the front of the alarm description indicate the location of the alarm. A sub-window is made available for the urgent alarms that have not been attended to. This structure provides a method of fast interaction with important aspects related to battery management.

[0132] An alternative battery monitoring architecture is shown in FIG. 13. This Figure shows the voltage sensors 1, temperature sensors 2 and current sensors 3 which are coupled to the bloc nodes 4 and bank nodes 5. Battery node 6 is also shown. In contrast to FIG. 1, the bloc nodes 4 associated with each string are coupled to a respective string bus 7, which in turn is connected to the common bus 8.

[0133] Where in the aforegoing description reference has been made to elements or integers having known equivalents, then such equivalents are included as though individually set forth.

[0134] Although the invention has been described by way of example and with reference to particular embodiments, it is understood that modifications and/or improvements can be made without departing from the scope thereof. 

1. A battery monitoring network including a battery node; one or more distributed nodes of a first class each including means for acquiring first battery variable information, processing means adapted to manipulate the first battery variable information, and a communication means for communicating with the battery node; and one or more distributed nodes of a second class each including means for acquiring second battery variable information, processing means adapted to manipulate the second battery variable information, and a communication means for communicating with the battery node.
 2. The network of claim 1 wherein the nodes of a first and/or second class each include a memory for storing the battery variable information and/or the results of manipulating the battery variable information.
 3. The network of claim 1 or 2 wherein the first battery variable information includes voltage information.
 4. The network of claim 1, 2 or 3 wherein the first battery variable information includes temperature information.
 5. The network of any of the preceding claims wherein the second battery variable information includes current information.
 6. The network of any of the preceding claims adapted to monitor a battery which includes a plurality of blocs each comprising one or more serially connected cells and a plurality of strings each comprising one or more serially connected blocs, the strings being connected in parallel with each other, wherein the distributed nodes of a first class are bloc nodes each adapted to acquire information relating to one or more of the blocs, and wherein the distributed nodes of a second class are bank nodes each adapted to acquire information relating to one or more of the strings.
 7. The network of any of the preceding claims wherein the number of distributed nodes of a first class exceeds the number of distributed nodes of a second class.
 8. The network of any of the preceding claims wherein the battery node includes a processor for manipulating data received from the distributed nodes.
 9. The network of any of the preceding claims wherein the battery node includes a graphical user interface.
 10. The network of any of the preceding claims including an internet interface coupled to the battery node.
 11. The network of any of the preceding claims wherein the distributed nodes of a first class are adapted to communicate with the distributed nodes of a second class.
 12. The network of any of the preceding claims, wherein the distributed nodes are arranged in two or more sub-networks, each sub-network communicating with the battery node via a respective sub-network junction.
 13. The network of claim 12 wherein each sub-network includes a respective router for routing data through the respective sub-network junction.
 14. The network of any of the preceding claims wherein the distributed nodes communicate with the battery node via a common bus.
 15. The network of any of the preceding claims wherein the battery node includes means for communicating data to the distributed nodes.
 16. The network of any of the preceding claims wherein each distributed node is adapted to receive battery variable information from a plurality of sensors.
 17. The network of any of the preceding claims wherein the distributed nodes of a first and/or second class are adapted to compare the battery variable information with one or more predetermined threshold values.
 18. The network of any of the preceding claims wherein the distributed nodes of a first class are adapted to acquire coup de fouet parameters during battery discharge.
 19. The network of any of the preceding claims adapted to monitor a valve regulated lead acid (VRLA) battery.
 20. A VRLA battery in combination with the network of claim
 19. 